Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refactor: Create method for skipping ParseObject keys #144

Merged
merged 4 commits into from
Jan 9, 2024

Conversation

cbaker6
Copy link
Member

@cbaker6 cbaker6 commented Jan 9, 2024

New Pull Request Checklist

Issue Description

Approach

TODOs before merging

  • Add tests
  • Add entry to changelog
  • Add changes to documentation (guides, repository pages, in-code descriptions)

@cbaker6 cbaker6 changed the title refactor: Create method for skipping Keys refactor: Create method for skipping ParseObject keys Jan 9, 2024
Copy link

codecov bot commented Jan 9, 2024

Codecov Report

Attention: 1 lines in your changes are missing coverage. Please review.

Comparison is base (e54ac22) 91.36% compared to head (098d3e1) 91.68%.

Files Patch % Lines
Sources/ParseSwift/Coding/ParseEncoder.swift 95.65% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #144      +/-   ##
==========================================
+ Coverage   91.36%   91.68%   +0.31%     
==========================================
  Files         178      178              
  Lines       15504    15511       +7     
==========================================
+ Hits        14165    14221      +56     
+ Misses       1339     1290      -49     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@cbaker6 cbaker6 merged commit 7b7116d into main Jan 9, 2024
14 checks passed
@cbaker6 cbaker6 deleted the noSkipKeysOnNonParseObjects branch January 9, 2024 20:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant